Release: Merge back 2.52.3 into dev from: master-into-dev/2.52.3-2.53.0-dev#13770
Release: Merge back 2.52.3 into dev from: master-into-dev/2.52.3-2.53.0-dev#13770
Conversation
….53.0-dev Release: Merge back 2.52.2 into bugfix from: master-into-bugfix/2.52.2-2.53.0-dev
Signed-off-by: kiblik <5609770+kiblik@users.noreply.github.com>
Co-authored-by: Paul Osinski <paul.m.osinski@gmail.com>
Co-authored-by: Paul Osinski <paul.m.osinski@gmail.com>
* 🐛 fix severity order of trivy #13647 * udpate, fix unittests * update * update
We are approving a boto3 rev almost every single day at this point. Let's skip the patches and only focus on the minor revs
…origin (#13740) * feat(serializers, filters): add choice fields for business criticality, platform, lifecycle, and origin * feat(serializers): allow null values for choice fields in ProductSerializer * feat(serializers): make choice fields optional in ProductSerializer
Now that this feature has been live for a while, I think we can reduce the logging a bit. Noticed a lot of logs for this during #13241
Publish documentation on pushes to bugfix in addition to master. This will be useful for fixing urgent documentation issues without waiting for a week for the next bugfix release
Add path filter for docs in gh-pages workflow
Release: Merge release into master from: release/2.52.3
🔴 Risk threshold exceeded.This pull request modifies several sensitive codepaths (serializers, filters, middleware, tasks) and flags those edits for review, fixes a middleware issue that previously served stale System_Settings (which could allow authorization/configuration bypass), changes the Trivy parser to trust report severity over CVSS (risking lower-than-appropriate severity assignment), and adds two externally-hosted JavaScript files to the docs without SRI (introducing a supply-chain/XSS risk).
🔴 Configured Codepaths Edit in
|
| Vulnerability | Configured Codepaths Edit |
|---|---|
| Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml. |
🔴 Configured Codepaths Edit in dojo/filters.py
| Vulnerability | Configured Codepaths Edit |
|---|---|
| Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml. |
🔴 Configured Codepaths Edit in dojo/middleware.py
| Vulnerability | Configured Codepaths Edit |
|---|---|
| Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml. |
🔴 Configured Codepaths Edit in dojo/tasks.py
| Vulnerability | Configured Codepaths Edit |
|---|---|
| Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml. |
Stale System Settings Leading to Authorization/Configuration Bypass in dojo/middleware.py
| Vulnerability | Stale System Settings Leading to Authorization/Configuration Bypass |
|---|---|
| Description | The System_Settings model contains numerous security-sensitive configurations, including password policies, API error exposure, and integration settings. Prior to this change, modifications to these settings might not have been immediately reflected due to the DojoSytemSettingsMiddleware serving stale data from its thread-local cache. This could lead to the application operating with outdated, less secure configurations, potentially resulting in authorization bypasses, weaker authentication enforcement, or information disclosure. |
django-DefectDojo/dojo/middleware.py
Lines 113 to 116 in c7b813f
Incorrect Severity Assignment in dojo/tools/trivy/parser.py
| Vulnerability | Incorrect Severity Assignment |
|---|---|
| Description | The Trivy parser now prioritizes the 'Severity' field directly from the Trivy report over any severity derived from CVSS scores. This can lead to an incorrectly low severity being assigned to a vulnerability if Trivy's reported severity is lower than the severity indicated by the CVSS score. This misrepresentation can result in improper risk assessment and delayed remediation of potentially critical issues. |
django-DefectDojo/dojo/tools/trivy/parser.py
Lines 266 to 282 in c7b813f
Third-Party Script Inclusion / Supply Chain Risk in docs/layouts/_partials/head/script-header.html
| Vulnerability | Third-Party Script Inclusion / Supply Chain Risk |
|---|---|
| Description | The code introduces two dynamically loaded third-party JavaScript files from static.reo.dev and assets.apollo.io into the docs section of the application. These scripts are loaded without Subresource Integrity (SRI) hashes. This creates a supply chain risk: if either of these external domains were compromised, an attacker could inject malicious JavaScript into the application, potentially leading to Cross-Site Scripting (XSS), data exfiltration, or session hijacking for users viewing the documentation. |
django-DefectDojo/docs/layouts/_partials/head/script-header.html
Lines 1 to 12 in c7b813f
We've notified @mtesauro.
All finding details can be found in the DryRun Security Dashboard.
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
….52.3-2.53.0-dev Release: Merge back 2.52.3 into dev from: master-into-dev/2.52.3-2.53.0-dev
Release triggered by
rossops